This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
Lot's of ways to skin this cat, and lot's of unknowns from my end, but one simple approach would be...
1. Notes Mail and mNotes on one box on LAN (not DMZ) at main office. I wouldn't put Mail servers in a DMZ as most users hit them from within. And I don't know of any installs where duplicate mail servers are thrown in DMZ just for iNotes access (too costly).
2. Notes Mail replicas on second server at branch office with Traveller, again, not in DMZ. Run Traveller on both servers after your initial testing.
3. Home user's on their local mail server.
4. If connection between offices is dedicated and connection speed is sufficient then clustering should be ok. If via Internet, enable port encryption between servers.
5. Keep in mind that users on home server would would need to hit iNotes via different URL if their site is down, unless you invest in heavy hardware to handle balancing, redirects, etc. Last time I checked, F5's BigIP was still a little pricey.
6. Sametime should go on dedicated server (IBM recommendation and mine too) at main office. Use slowest box for now due to low usage.
7. Firewalls need to allow Notes traffic between each office for replication, and port 443 inbound for iNotes (yes invest in and set up SSL).
8. All SMTP will naturally come in to main office by default before routing to branch office. Although, Domain MX records should be set up to try main office first and then branch office 2nd.
Email me if you have any questions (tomharrison08@gmail.com)
Feedback response number WEBB7S7RSN created by ~Sven Zeknukonyoni on 05/19/2009
My thoughts...
Return to top
. . My thoughts... (~Sven Zeknukony... 19.May.09) 
